-
-
Notifications
You must be signed in to change notification settings - Fork 55
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CSL #66
Conversation
Sorry if this is a silly question - should this allow me to use CSL YAML/JSON (output by Zotero) as the input format for the Hayagriva CLI? Or is this MR only for using the XML schema for the citation style? |
I'm wondering this too. It seems that hayagriva is not able to parse CSL yaml files currently: |
Yes, this PR is only about CSL style files. I implemented CSL-JSON support for testing only (not exposed for library users), and right now, the structs are generic in such a way that CSL-JSON cannot be mixed with BibLaTeX/Hayagriva YAML. It could be a good contribution to allow users to bring CSL-JSON and mix it with other bibliographic formats. |
This PR implements CSL. cf. #32, typst/typst#2406, typst/typst#132
All known styles are tested to the extent that they don't cause a panic.
The following remains to do:
Correctly map the CSL concept of original metadata onto Hayagriva entries in Taxonomy.Change Serial Number type to a dictionary and remove top-leveldoi
etc. fromEntry
givenname-disambiguation-rule
is not applied to disambiguate names within a cite.collapse="year"
deletes the year, but not the surrounding delimiters. It should rerender the item instead.collapse="year-suffix"
andcollapse="year-suffix-ranged"
is ignored.subsequent-author-substitute
is ignored.Maybe we should also use the test suite, however, this would require injecting CSL variables directly, bypassing the
Entry
struct.